Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1088

reference
520-tree-1
name
1088
tree-preservation-order

undefined

520-tpo-1
uprn
address-text
point
POINT (-1.022206 50.897512)
geometry
MULTIPOLYGON (((-1.022164 50.897508,-1.022166 50.897516,-1.022172 50.897524,-1.022181 50.897530,-1.022193 50.897534,-1.022206 50.897535,-1.022219 50.897534,-1.022231 50.897530,-1.022241 50.897524,-1.022247 50.897517,-1.022249 50.897508,-1.022247 50.897500,-1.022241 50.897492,-1.022232 50.897486,-1.022220 50.897482,-1.022207 50.897481,-1.022194 50.897482,-1.022182 50.897486,-1.022172 50.897492,-1.022166 50.897499,-1.022164 50.897508)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL